Add configurable container resource requests and limits via CR spec - #27
Conversation
689bf70 to
afd7706
Compare
afd7706 to
66f5db6
Compare
|
/retest |
1 similar comment
|
/retest |
lpiwowar
left a comment
There was a problem hiding this comment.
Just very quickly skimmed through it and there is one thing that crossed my mind we should try IMO but overall I like the PR 👍.
479d7e8 to
652455c
Compare
|
/retest |
228d137 to
b529180
Compare
328b200 to
df8997a
Compare
df8997a to
bd3a911
Compare
|
/retest |
|
Change overall looks fine. I think the version bumps and the Init containers at least we should think a bit more before exposing it. The version bumps looks unrelated to the change (and should at least be on it's own commit). And the Init containers seems like a leak from internal implementation to CR. |
Addresses a security vulnerability in the x/text package. The transitive dependency bumps (x/mod, x/net, x/sync, x/sys, x/term, x/tools) are required by the new x/text version.
bd3a911 to
ae02a43
Compare
|
/retest |
Allow users to override CPU/memory requests and limits for user-facing containers (llamaStack, lightspeedService, postgres, okp, consolePlugin) through the OpenStackLightspeed CR spec. Internal containers (dataverse exporter, vector-database init) keep hardcoded defaults since they are implementation details not exposed to users. Defaults are applied by the API server via kubebuilder markers.
ae02a43 to
07d805f
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: omkarjoshi0304, umago The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
Summary
This adds a
spec.resourcesfield to the OpenStackLightspeed CR that accepts per-containercorev1.ResourceRequirementsoverrides following the same pattern used by other openstack-k8s-operators (e.g. test-operator). Defaults are declared via kubebuilder:default markers on the API types, so the API server sets them automatically — no fallback logic needed in the controllers.How it works
Example CR
Test Proof